Anomalous input detection

ABSTRACT

Method and apparatus are disclosed for interface verification for vehicle remote park-assist. An example vehicle system includes a mobile device and a vehicle autonomy unit. The mobile device includes a touchscreen and a controller. The controller is to present, via the touchscreen, an interface of a remote parking app and receive, via the touchscreen, an input responsive to the presentation of the interface. The vehicle autonomy unit receives an input signal from the mobile device and an input classifier coupled to the vehicle autonomy unit verifies the received input signal complies with an input classification.

TECHNICAL FIELD

The present disclosure generally relates to remote park-assist and, morespecifically, input verification for vehicle remote park-assist.

BACKGROUND

Many vehicles include functions in which at least some motive functionsof a vehicle are autonomously controlled by the vehicle. For example,some vehicles include cruise control in which the vehicle controlsacceleration and/or deceleration of the vehicle so that a speed of thevehicle is maintained. Some vehicles also include adaptive cruisecontrol in which the vehicle controls acceleration and/or decelerationof the vehicle so that a speed of the vehicle is maintained while alsomaintaining a predetermined following distance from other vehiclesahead. Further, some vehicles include park-assist features in which thevehicle autonomously controls motive functions of the vehicle to parkthe vehicle into a parking spot.

SUMMARY

The appended claims define this application. The present disclosuresummarizes aspects of the embodiments and should not be used to limitthe claims. Other implementations are contemplated in accordance withthe techniques described herein, as will be apparent to one havingordinary skill in the art upon examination of the following drawings anddetailed description, and these implementations are intended to bewithin the scope of this application.

Example embodiments are shown for input verification for vehicle remotepark-assist. An example disclosed vehicle system includes a mobiledevice including a touchscreen configured to present an interface of aremote parking app. The touchscreen receives an input responsive to theremote parking app. The vehicle system further includes a vehicleautonomy unit communicably coupled to the mobile device to receive aninput signal which corresponds with the received input. An inputclassifier is coupled to the vehicle autonomy unit and the inputclassifier verifies the received input signal complies with an inputclassification. The vehicle autonomy unit sends a notification to themobile device if the received input signal is non-compliant with theinput classification.

An example disclosed method for verifying inputs for remote parking ofvehicles includes presenting, via a touchscreen of a mobile device, aninterface of a remote parking app. The method further includes receivingan input at a controller of the mobile device via the touchscreenresponsive to presenting the interface. The method further includesreceiving, via a vehicle autonomy unit, an input signal send by themobile device and verifying, by an input classifier, the received inputsignal complies with an input classification. The method furtherincludes sending, via the vehicle autonomy unit, a notification to themobile device if the received input signal is non-compliant with theinput classification.

An example disclosed tangible computer readable medium includesinstructions which, when executed, cause a machine to present, via atouchscreen of a mobile device, an interface of a remote parking app.The instructions which, when executed, also cause the machine to receivean input at a controller via the touchscreen responsive to presentingthe interface. The instructions, when executed, further cause themachine to receive, by a vehicle autonomy unit, an input signal sent bythe mobile device, verify, by an input classifier, the received inputsignal complies with an input classification, and send, via the vehicleautonomy unit, a notification to the mobile device if the received inputsignal is non-compliant with the input classification.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the invention, reference may be made toembodiments shown in the following drawings. The components in thedrawings are not necessarily to scale and related elements may beomitted, or in some instances proportions may have been exaggerated, soas to emphasize and clearly illustrate the novel features describedherein. In addition, system components can be variously arranged, asknown in the art. Further, in the drawings, like reference numeralsdesignate corresponding parts throughout the several views.

FIG. 1 illustrates an example mobile device utilized for remote parkingof an example vehicle in accordance with the teachings herein.

FIG. 2 illustrates an example remote park-assist interface presented viathe mobile device of FIG. 1.

FIG. 3 illustrates another example remote park-assist interfacepresented via the mobile device of FIG. 1.

FIG. 4A illustrates another example remote park-assist interfacepresented via the mobile device of FIG. 1.

FIG. 4B illustrates another example remote park-assist interfacepresented via the mobile device of FIG. 1.

FIG. 5 is a block diagram of the mobile device and the vehicle of FIG.1.

FIG. 6 is a block diagram of electronic components of the mobile deviceof FIG. 1.

FIG. 7 is a block diagram of electronic components of the vehicle ofFIG. 1.

FIG. 8 is a flowchart for verifying an interface of a mobile device forremote parking of a vehicle in accordance with the teachings herein.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS

While the invention may be embodied in various forms, there are shown inthe drawings, and will hereinafter be described, some exemplary andnon-limiting embodiments, with the understanding that the presentdisclosure is to be considered an exemplification of the invention andis not intended to limit the invention to the specific embodimentsillustrated.

Many vehicles include functions in which at least some motive functionsof a vehicle are autonomously controlled by the vehicle. For example,some vehicles include cruise control in which the vehicle controlsacceleration and/or deceleration of the vehicle so that a speed of thevehicle is maintained. Some vehicles also include adaptive cruisecontrol in which the vehicle controls acceleration and/or decelerationof the vehicle so that a speed of the vehicle is maintained while alsomaintaining a predetermined following distance from other vehiclesahead.

Further, some vehicles include park-assist features (e.g., a remotepark-assist feature) in which the vehicle autonomously controls motivefunctions of the vehicle to park the vehicle into a parking spot. Aremote park-assist feature autonomously parks a vehicle when a driver ofthe vehicle has already exited the vehicle. For example, the driver mayposition the vehicle near a parking spot, exit the vehicle, and remotelyinstruct the vehicle (e.g., via a pushing a button or performing aprescribed action on a key fob or mobile device) to autonomously park inthe parking spot. A driver may utilize remote parking to park a vehiclein a parking spot in which a driver would subsequently be unable to exita cabin of the vehicle (e.g., due to a nearby vehicle, wall, or otherstructure).

The example apparatus, methods, and machine readable media include aremote park-assist system for initiating autonomous parking of a vehicleinto parking spot. A mobile device enables a driver to initiateautonomous parking movement while the driver is located outside of thevehicle. As used herein, “remote parking” and “remote park-assist” referto a vehicle controlling motive functions of the vehicle without directsteering or velocity input from a driver to autonomously park thevehicle into a parking spot while the driver is located outside of thevehicle. For example, a remote park assist-system enables an autonomyunit to control the motive functions of the vehicle to remotely park thevehicle into the parking spot upon initiation from the driver.

The driver moves his or her finger along a touchscreen (e.g.,capacitive, resistive) of the mobile device to initiate the autonomousparking movement. The remote park-assist system detects whether thetouchscreen has received an input consistent with the initiation of theautonomous parking movement. The remote-park assist system includesdetection of nominal inputs and anomalous inputs received via the touchscreen of the mobile device. The remote-park assist system furtheranalyzes the detected input to determine whether the input is consistentwith the autonomous parking movement while controlling functions of avehicle via the mobile device. In some examples, the remote-park assistsystem includes an input classifier that utilizes a machine learningalgorithm to determine, as a binary classification, whether a receivedinput was a nominal input (e.g., an intended input) or an anomalousinput (e.g., an unintended input). If the input classifier determinesthe input is an anomalous input, the remote park-assist system presentsa notification via the touchscreen. In certain embodiments, thenotification includes an acknowledgement checkbox via the touchscreenand the remote park-assist system subsequently pauses and/or stopsperformance of the vehicle functions until the acknowledgement checkboxis selected. Additionally, in certain embodiments, the input classifierdetects a source of the anomalous inputs, and the remote park-assistsystem identifies the source and the notification includes presentingthe source of the anomalous input.

Turning to the figures, FIG. 1 illustrates an example mobile device 100that is utilized for remote parking an example vehicle 102 in accordancewith the teachings herein. The vehicle 102 may be a standard gasolinepowered vehicle, a hybrid vehicle, an electric vehicle, a fuel cellvehicle, and/or any other mobility implement type of vehicle. Thevehicle 102 includes parts related to mobility, such as a powertrainwith an engine, a transmission, a suspension, a driveshaft, wheels, etc.The vehicle 102 may be semi-autonomous (e.g., some routine motivefunctions controlled by the vehicle 102) or autonomous (e.g., motivefunctions are controlled by the vehicle 102 without direct driverinput).

As illustrated in FIG. 1, the vehicle 102 is positioned to be remotelyparked in an available parking spot 104. The available parking spot 104is positioned between an occupied parking spot 106 (e.g., a firstoccupied parking spot) that is occupied by a parked vehicle 108 (e.g., afirst parked vehicle) and another occupied parking spot 110 (e.g., asecond occupied parking spot) by another parked vehicle 112 (e.g., asecond parked vehicle). In the illustrated example, the availableparking spot 104 is a parallel parking spot. In other examples, theavailable parking spot 104 into which the vehicle 102 is to park is aperpendicular or other non-parallel parking spot. In the illustratedexample, the vehicle 102 is positioned next to the occupied parking spot110 and/or the parked vehicle 112 to enable the vehicle 102 to beparallel parked in the available parking spot 104 via remotepark-assist.

The vehicle 102 of the illustrated example includes an autonomy unit114. The autonomy unit 114 is an electronic control unit (ECU) of thevehicle 102 that autonomously controls motive functions of the vehicle102 to remotely park the vehicle 102 in available parking spots (e.g.,the available parking spot 104) and/or otherwise autonomously drives thevehicle 102. For example, the autonomy unit 114 controls the motivefunctions of the vehicle 102 based on data collected from sensor(s) ofthe vehicle 102 (e.g., sensors 704 of FIG. 7).

The vehicle 102 also includes a communication module 116 (e.g., a firstcommunication module). For example, the communication module 116 is ashort-range wireless module for wireless communication with mobiledevice(s) of user(s) of the vehicle 102. In the illustrated example, thecommunication module 116 is communicatively connected to the mobiledevice 100 of a user 118 of the vehicle 102. The communication module116 includes hardware and firmware to establish a connection with themobile device 100. In some examples, the communication module 116implements the Bluetooth® and/or Bluetooth® Low Energy (BLE) protocols.The Bluetooth® and BLE protocols are set forth in Volume 6 of theBluetooth® Specification 4.0 (and subsequent revisions) maintained bythe Bluetooth® Special Interest Group. In other examples, thecommunication module 116 may use WiFi, WiMax, NFC, UWB (Ultra-WideBand), and/or any other communication protocol that enables thecommunication module 116 to communicatively couple to the mobile device100.

Prior to communicating with the mobile device 100, the communicationmodule 116 may authenticate the mobile device 100 for communication withthe communication module 116. To authenticate communication between thecommunication module 116 and the mobile device 100, the communicationmodule 116 intermittently broadcasts a beacon (e.g., a low-energy beaconsuch as Bluetooth® low-energy (BLE) beacon). When the mobile device 100is within a broadcast range of the communication module 116, the mobiledevice 100 receives the beacon and subsequently sends a key. Thecommunication module 116 authenticates the mobile device 100 forcommunication module 116 upon receiving the key from the mobile device100. In other examples, the mobile device 100 broadcasts a beacon andthe communication module 116 subsequently receives the beacon toauthenticate communication between the mobile device 100 and thecommunication module 116.

In the illustrated example, the user 118 (e.g., a driver or otheroccupant of the vehicle 102) utilizes the mobile device 100 (e.g., asmart phone, a smart watch, a wearable, a tablet, etc.) to initiateremote parking of the vehicle 102 into the available parking spot 104.As illustrated in FIG. 1, the mobile device 100 includes a communicationmodule 120 and a touchscreen 122.

The communication module 120 communicatively connects with othercommunication modules. For example, the communication module 120 is ashort-range wireless module that wirelessly connects to thecommunication module 116 to establish communication between the mobiledevice 100 and the vehicle 102. The communication module 120 includeshardware and firmware to establish a connection with the communicationmodule 116 of the vehicle 102. In some examples, the communicationmodule 116 implements Wi-Fi, Bluetooth® and/or Bluetooth® Low Energy(BLE) protocols.

The touchscreen 122 of the mobile device 100 provides an interface(e.g., an interface 200 of FIG. 2, an interface 300 of FIG. 3, aninterface 400 of FIGS. 4A and 4B) between the user 118 and the mobiledevice 100 to enable the user 118 to initiate remote parking of thevehicle 102. For example, the touchscreen 122 is a resistivetouchscreen, a capacitive touchscreen, and/or any other type oftouchscreen that displays output information to and tactilely receivesinput information from the user 118 of the mobile device 100. In someexamples, the mobile device 100 also includes other input devices (e.g.,buttons, knobs, microphones, etc.) and/or output devices (e.g.,speakers, LEDs, haptic transducers, etc.) to receive input informationfrom and/or provide output information to the user 118 of the mobiledevice 100. In operation, the user 118 interacts with the touchscreen122 for initiating remote parking of the vehicle 102 via the mobiledevice 100. Based on input received from the user 118 via thetouchscreen 122, the communication module 120 of the mobile device sendsa signal 124 to the communication module 116 of the vehicle 102 thatinstructs the autonomy unit 114 to initiate remote parking of thevehicle 102. Initiation of remote parking continues as the touchscreen122 continues to receive an input from the user 118.

FIG. 2 illustrates an example user interface 200 displayed or otherwisepresented by a touchscreen (e.g., the touchscreen 122 of FIG. 1) inaccordance with the teachings herein. The interface 200 includes amotion track 202 presented, via the touchscreen 122, to the user (e.g.,user 118 of the mobile device 100 of FIG. 1) during remote parking ofthe vehicle. In some examples, the motion track 202 is presented oncethe autonomy unit 114 initiates remote parking of the vehicle 102 todefine an input pathway for the user 118 to follow while performing amaneuver during remote parking of the vehicle. In some examples, theuser 118 continuously interacts with the motion track 202 by drawing amotion path 204 on the touchscreen 122 within the motion track 202 suchthat the autonomy unit 114 continues to remotely park the vehicle 102within the available parking spot 104 as long as the touchscreen 122continues to detect an input and/or movement within the motion track202.

As illustrated in FIG. 2, the motion track 202 is defined by an innerboundary 206 and an outer boundary 208. The inner boundary 206 and theouter boundary 208 are spaced apart by a distance, percentage, and/or anumber of pixels of the touchscreen 122 such that the motion track 202has a width 210 defined by the distance and/or the number of pixelsbetween the inner boundary 206 and the outer boundary 208. In someexamples, the width 210 of the motion track 202 is predefined by theuser 118 and/or software utilized for remote parking the vehicle 102 viathe mobile device 100. While the motion track 202 is illustrated as acircle, it will be understood that other shapes, symbols, icons andconfigurations may be used for display of the motion track 202.

The interface 200 of FIG. 2, shows the motion path 204 associated withan input the user 118 provides via the touchscreen 122 to initiateand/or continue remote parking of the vehicle 102. The motion path 204is displayed as a contiguous line that the user 118 draws within themotion track 202 via the touchscreen 122. As illustrated in FIG. 2, themotion path 204 includes an initiation input 212 and a travel point 214opposite the travel point 214. The initiation input 212 corresponds to alocation on the touchscreen 122 at which the user 118 begins to draw themotion path 204. The travel point 214 corresponds to a location on thetouchscreen 122 at which the user 118 is currently touching or pressingthe touchscreen 122 to continue drawing the motion path 204. In someexamples, the initiation input 212 is represented by an arrow pointingin the direction the user 118 draws the motion path 204 and the travelpoint 214 is a dot showing the current location of the motion path 204;however other symbols an icons are possible to represent the initiationinput 212 and/or the travel point 214.

In some examples, the interface 200 further includes a confidence band216 surrounding the motion track 202. Similar to the motion track 202,the confidence band 216 has an inner band boundary 218 and an outer bandboundary 220. The inner band boundary 218 and the outer band boundary220 are spaced apart by a distance and/or a number of pixels of thetouchscreen 122 such that the confidence band 216 has a width 222defined by the distance and/or the number of pixels between the innerband boundary 218 and the outer band boundary 220. In some examples, thewidth 222 of the confidence band 216 is predefined by the user 118 todefine an area of the touchscreen 122 where input is expected to occurwhile remote parking the vehicle 102. In other such examples, the width222 of the confidence band 216 is defined by the software utilized forremote parking the vehicle 102 via the mobile device 100. The softwaredefines the width 22 based on a historical data analysis of a pluralityof motion paths 204 collected by the mobile device 100, via thetouchscreen 122, during a plurality of previous remote parkingoccurrences of the vehicle 102. As such, the width 222 of the confidenceband 216 defines an area of the touchscreen 122, based on the historicaldata analysis of the motion path 204, where the software expectsintended input by the user 118 during remote parking of the vehicle 102.The motion track 202 is included within the width 222 of the confidenceband 216, and as shown in FIG. 2, the motion track 202 is centeredwithin the confidence band 216. However, based on the historicalanalysis results, performed by the software, the confidence band 216 maybe placed in an alternative position relative to the motion track 202.

In some examples, the touchscreen 122 detects an input that correspondswith the initiation input 212, the travel point 214, and points of themotion path 204 therebetween to determine whether the mobile device 100is to send the signal 124 to the autonomy unit 114 of the vehicle 102 toinitiate and continue remote parking of the vehicle 102. For example,based on the information collected by the touchscreen 122, the mobiledevice 100 determines whether the travel point 214 is moving within themotion track 202. Further, in some examples, the mobile device 100determines in which direction the travel point 214 is moving within themotion track 202 by comparing the travel point 214 (i.e., the currentlocation) to the initiation input 212 (i.e., the starting location) andall points detected on the motion path 204 therebetween. Based on themovement of the travel point 214 on the interface 200 detected via thetouchscreen 122, the mobile device 100 wirelessly sends a communicationsignal (e.g., the signal 124 of FIG. 1) to the autonomy unit 114 of thevehicle 102, via the communication module 116 and the communicationmodule 120, to initiate and/or continue remote parking of the vehicle102.

In some examples, the mobile device 100 is configured to send the signal124 to initiate and/or perform remote parking of the vehicle 102 suchthat the autonomy unit 114 continues to remotely park the vehicle 102 aslong as the touchscreen 122 continues to detect movement of the travelpoint 214 within the motion path 204. That is, the autonomy unit 114performs both forward and backward maneuvers during remote parking thevehicle 102 in response to the touchscreen 122 continuing to detectmovement of the travel point 214 within the motion track 202 (e.g., in aclockwise direction and/or a counterclockwise direction).

In some examples, the mobile device 100 is configured to send the signal124 to initiate movement of the vehicle 102 in a particular directionduring remote parking based on the detected direction of movement of thetravel point 214 within the motion track 202. For example, thecommunication module 120 of the mobile device 100 sends the signal 124to the vehicle 102 to initiate forward motion during remote parking ofthe vehicle 102 in response to the touchscreen 122 detecting that thetravel point 214 is moving in a clockwise direction within the motiontrack 202. In some such examples, the communication module 120 of themobile device 100 sends the signal 124 to initiate backward motionduring remote parking of the vehicle 102 in response to the touchscreen122 detecting that the travel point 214 is moving in a counterclockwisedirection within the motion track 202. In other such examples, movementof the travel point 214 in the counterclockwise direction corresponds toforward motion of the vehicle 102, and movement of the travel point 214in the clockwise direction corresponds to backwards motion of thevehicle 102. Further, in other examples, the motion track 202 of theinterface 200 is designated only for initiating forward motion duringremote parking when the travel point 214 is moving in the clockwisedirection within the motion track 202.

Further, in some examples, a speed of motion of the travel point 214detected via the touchscreen 122 corresponds to a travel speed of thevehicle 102 during remote parking. For example, the faster the user 118moves the travel point 214 along the touchscreen 122, the faster theautonomy unit 114 moves the vehicle 102 during remote parking. Likewise,the slower the user 118 moves the travel point 214 along the touchscreen122, the slower the autonomy unit 114 moves the vehicle 102 duringremote parking.

FIG. 3 illustrates another example interface 300 of the touchscreen 122of the mobile device 100, as shown in FIG. 1. In accordance with theteachings herein, the interface 300 includes the motion track 202surrounded by the confidence band 216. A plurality of motion paths 302received from the user 118 to initiate and/or perform remote parking ofthe vehicle 102 are shown within the inner boundary 206 and the outerboundary 208 defined by the motion track 202 and the inner boundary 218and the outer boundary 220 defined by the confidence band 216. Forexample, to initiate and continue remote parking of the vehicle 102, theuser 118 provides an initiation input 304 and draws the first motionpath 302 a, the second motion path 302 b, and the third motion path 302c in a continuous motion along the motion path. Travel point 306represents the current location of the input provided by the user 118 tothe touchscreen 122 on the third motion path 302 c. In some examples,the continuous input provided by the user (e.g., first motion path 302a, second motion path 302 b, third motion path 302 c) sometimes fallsoutside the motion track 202 and the confidence band 216. However, thefirst motion path 302 a, the second motion path 302 b, and the thirdmotion path 302 c, each follow a continuous motion path in a directionaround the motion track 202. That is, while some portions of the firstmotion path 302 a, the second motion path 302 b, and the third motionpath 302 c, stray outside of the motion track 202, the motion paths arestill within the confidence band 216. As such, each motion pathrepresents a continuous and expected input provided by the user 118during remote parking of the vehicle 102.

FIG. 4A illustrates another example interface 400 of the touchscreen ofthe mobile device 100, as shown in FIG. 1. In accordance with theteachings herein the interface 400 includes the motion track 202surrounded by the confidence band 216. A plurality of unintended and/oranomalous inputs 402 received by the touchscreen 122 are shown insideand outside of the boundaries defined by the motion track 202 and theconfidence band 216. In some examples, the unintended and/or anomalousinputs 402 are related to an intended input by the user 118 to initiateand continue remote parking of the vehicle 102. Alternatively, theunintended and/or anomalous inputs 402 are not related or unrelated toan intended input by the user 118 to initiate and/or continue remoteparking of the vehicle 102. For example, to initiate remote parking ofthe vehicle 102, the user 118 provides an initiation input 404 (i.e.,intended input) and draws the first motion path 402 a (e.g., firstanomalous input) along the motion track 202. The touchscreen 122 detectsthe initiation input 404 provided by the user 118. However, thetouchscreen 122 detects the first motion path 402 a as a non-continuousinput that fails to follow a continuous path around the motion track202. For example, the first motion path 402 a includes a gap between thetwo portions of the path indicating the first notion path 402 a wasdetected as a non-continuous path. The touchscreen 122 further detects afirst anomalous input 402 b, a second anomalous input 402 c, a thirdanomalous input 402 d, and a fourth anomalous input 402 e, randomlydistributed around the touchscreen 122. In some examples, the firstmotion path 402 a, the first anomalous input 402 b, the second anomalousinput 402 c, the third anomalous input 402 d, and the fourth anomalousinput 402 e, are unintended inputs detected by the touchscreen 122 inareas that are both inside and outside of the boundaries defined by themotion track 202 and the confidence band 220.

FIG. 4B illustrates the interface 400 further including a notificationbox 406 and a notification acknowledgment input 408. In some examples,the mobile device 100 displays the notification box 406 to the user whenan unintended and/or anomalous input (e.g., first motion path 402 a andanomalous inputs 402 b to 402 e of FIG. 4A) is detected by thetouchscreen 122. In some examples, the notification box 406 informs theuser that an unintended and/or anomalous input has been detected and theuser of the mobile device 100 is to confirm the touchscreen 122 isclean, dry and absent of any surface debris. Additionally and/oralternatively, the notification box 406 includes a plurality of possiblecauses for the detection of an anomalous input, such as but not limitedto, using mobile device 100 in the rain, user's hands are wet, user iswearing gloves, user is holding mobile device 100 at touchscreen 122periphery, and other such causes. Accordingly, in some examples thenotification includes suggestions to the user 118 to correct thedetection of anomalous inputs. For example, the notification box 406includes a text message that informs the user of the mobile device 100to confirm their hands are clean, dry and properly positioned on themobile device 100, confirm the touchscreen 122 is clean and dry, andother such messages. In some examples, the notification box 406 includesthe acknowledgement input 408 which requires the user of the mobiledevice 100 to provide an input (e.g., check a box) to theacknowledgement input 408 to confirm the notification was received.

As used herein, “unintended and/or anomalous inputs” are defined as agenerally unintended input detected by the touchscreen 122 of the mobiledevice 100 and/or a generally intended input that is incorrectlydetected by the touchscreen 122. In one non-limiting example, the firstmotion path 402 a of FIG. 4A, illustrates a generally intended inputthat is incorrectly detected by the touchscreen 122 of the mobile device100. As discussed above, the touchscreen 122 of the mobile device 100 isa resistive touchscreen, a capacitive touchscreen, and/or any other typeof touchscreen that displays output information to and tactilelyreceives input information from the user 118 of the mobile device 100.For example, the user 118 provides input to the touchscreen 122 using afinger, or other such input device compatible with the mobile device100, to contact the touchscreen 122. In some examples, the inputprovides an initial input to initiate the remote parking of the vehicle.In other such examples, the input draws the motion path 204 around themotion track 202 to provide continuous input during remote parking ofthe vehicle.

One known issue with receiving tactile input from the user 118 isinterference between the user's finger and the touchscreen 122. Forexample, wearing gloves, designed for use with the touchscreen 122, canprovide interference between the user's finger and the touchscreen 122.As such, use of gloves while holding and interacting with the mobiledevice 100 can cause the touchscreen 122 to detect unintended and/oranomalous inputs. The gloves tend to work with mixed results such thatthe touchscreen 122 generally detects intended input from the user 118wearing the gloves. However, there are instances where performance ofthe gloves provides inconsistent and/or unsatisfactory results where thetouchscreen 122 detects an input that does not match the user's input.For example, the first motion path 402 a illustrates an intended inputfrom the user that is incorrectly detected by the touchscreen 122. Theinitiation input 404 provided by the user 118 is detected within themotion track 202 and the touchscreen 122 detects the first motion path402 a moving within the boundaries of the motion track 202 and theconfidence band 216. However, in this instance, the touchscreen 122detects the first motion path 402 a as a non-continuous motion path thatincludes a gap along the intended continuous pathway drawn by the userto continue remote parking of the vehicle 102. As such, user may becomeconfused and/or frustrated that the touchscreen 122 failed to correctlydetect the intended input. Additionally, the remote parking of thevehicle may be paused or even halted because the touchscreen 122 failedto correctly detect the intended input.

In another such example, the first anomalous input 402 b, the secondanomalous input 402 c, the third anomalous input 402 d, and the fourthanomalous input 402 e, illustrate a plurality of unintended and/oranomalous inputs detected by the touchscreen 122 of the mobile device100. For example, the anomalous inputs 402 b, 402 c, 402 d, and 402 e,are caused by an errant or unintended input provided by a finger, thepalm of the hand, or other such unintended input detected by thetouchscreen 122. In another such example, the anomalous inputs 402 b,402 c, 402 d, and 402 e are caused by an unintended input, such as butnot limited to, rain droplets, sweat droplets, dirt, or other suchunintended input detected by the touchscreen 122. As such, the anomalousinputs 402 b, 402 c, 402 d, and 402 e, are not consistent with inputsprovided by the user of the mobile device 100. In some examples, theanomalous inputs 402 b, 402 c, 402 d, and 402 e are detected by themobile device 100 after the user stops providing input to thetouchscreen 122.

In some examples, the remote parking system is configured to determineor otherwise classify a difference between a nominal input and ananomalous input. In one such example, the autonomy unit 114 of FIGS. 1and 5, includes an input classifier (e.g., input classifier 502 of FIG.5) configured to determine whether the detected input is consistent witha predetermined range of an expected input (e.g., within motion track202 and confidence band 216 of FIG. 2) or whether the detected input isconsistent with a predetermined range of an unexpected and/or anomalousinput (e.g., outside the motion track 202 and confidence band 216). Thatis, nominal inputs are expected to have a consistent behavior detectedwithin a certain location of the touchscreen 122 and anomalous inputstend to have a more inconsistent and random behavior detected by thetouchscreen 122. For example, the user of the mobile device 100 mayprovide input outside of the motion track 202 and/or the confidence band216 while providing the continuous input (e.g., motion paths 302 a, 302b, 302 c) during remote parking of the vehicle 102. Accordingly, in someexamples the input classifier 502 includes a timer that is used todetermine whether the inputs detected by the touchscreen 122 are nominalinputs or anomalous inputs. As such, the input classifier 502 furtherincludes a predetermined threshold for the number of anomalous inputsdetected within a specified time. If the number of detected anomalousinputs exceeds the predetermined threshold the user is notified (e.g.,presentation of notification box 406)

In some examples, input detected by the touchscreen 122 during remoteparking of the vehicle 102 is classified as anomalous, by the inputclassifier 502, based on one or more of the following criteria: (1)input detected by touchscreen 122 is outside the boundary defined by themotion track 202 and/or confidence band 216; (2) a plurality of inputspersistently detected at a specific location of the touchscreen 122beyond a predefined threshold of time; (3) a plurality of inputspersistently detected in area outside of the motion track 202 and/orconfidence band 216 (e.g., liquid droplets on screen); (4) consecutivechanges in variation in the angular velocity direction of the inputdetected by the touchscreen 122; (5) significant jumps in position ofconsecutive inputs detected by the touchscreen 122; and/or (6) repeatedcrossing of the circular pathway defined by the motion track 202 and theconfidence band 216. In addition to the anomalous input criteria above,a continuous input provided by the user 118 (e.g., motion path 204, 302a, 302 b, 302 c) during initiation and/or continuation of remote parkingof the vehicle 102, is classified as anomalous, by the input classifier502, based on one or more of the additional criteria: (1) detected inputfails to cross the initiation input 212, 304, of the motion pathfollowing a predetermined number of inputs received by the touchscreen122; (2) detected input fails to cross the initiation input 212, 304, ofthe motion path within a predetermined time; and/or (3) detected inputfails to cross checkpoints on the motion track 202 within apredetermined time. In some examples, the input classifier 502 isconfigured to prevent anomalous input detection from causing undesiredinput processing and/or activation of one or more modes of the remoteparking application (e.g., application 506 of FIG. 5). For example, ananomalous and/or undesired input can cause undesired activation orprocessing of remote parking application modes, such as but not limitedto, unlock/initiation, start a maneuver, pause a maneuver, and othersuch modes. As such, the input classifier 502 is further configured toclassify a detected input as an anomalous input based on one or more ofthe following criteria: (1) repeated and/or persistent input detectionoutside of valid touchscreen 122 areas (e.g., unlock button, motiontrack 202, confidence band 216, etc.); (2) repeated and/or persistentactivation of a specific touchscreen 122 location greater than apredetermined time threshold; (3) significant jump in touchscreen 122location for consecutively detected inputs; and (4) repeated and/orpersistent multi-location inputs detected on the touchscreen 122 (e.g.,rain droplets on screen, activation at screen edge, etc.).

In some embodiments, the input classifier 502, is an intelligent inputclassifier that includes one or more machine learning models and/oralgorithms, such as but not limited to, a support vector machine, anartificial neural network, a convolutional neural network, and othersuch models and/or algorithms. Accordingly, the intelligent inputclassifier 502 is taught or otherwise trained to classify inputs usinginput data from known nominal inputs and anomalous inputs. In onenon-limiting example, the intelligent input classifier 502 is trainedthat nominal inputs include continuous motion paths within the definedboundary of the motion track 202 and/or confidence band 216 of FIG. 3,(e.g., motion paths 302 a, 302 b, 302 c). The intelligent inputclassifier 502 is further trained that unintended and/or anomalousinputs include non-continuous motion paths (e.g., motion path 402 a) andunintended inputs detected by the touchscreen 122 (e.g., anomalousinputs 402 b, 402 c, 402 d).

In some examples, the intelligent input classifier 502 is furtherconfigured to distinguish between different anomalous inputs detected bythe touchscreen 122. For example, the intelligent input classifier 502is trained to identify input data such as the non-continuous motion path402 a is caused by input by a user wearing gloves. Additionally, theintelligent input classifier 502 is trained to identify the unintendedinputs 402 b, 402 c, 402 d, 402 e caused by input data, such as but notlimited to, liquid droplets present on the touchscreen, the user holdingor contacting a periphery of the touchscreen 122, or other suchunintended inputs. In some examples, the intelligent input classifier502 is configured to apply criteria to filter or reject a detected inputthat is clearly identified as an anomalous and/or intended input such asbut not limited to, repeated and/or persistent multi-location inputsdetected on the touchscreen 122 (e.g., rain droplets on screen,activation at screen edge, etc.), repeated and/or persistent activationof a specific touchscreen 122 location greater than a predetermined timethreshold, and repeated and/or persistent input detection around thetouchscreen 122 edge. In some embodiments, the intelligent inputclassifier 502 applies criteria to filter and/or reject detectedanomalous inputs after receipt of the acknowledgement input 408 from theuser of the mobile device 100. For example, in response to the detectionan anomalous input, the autonomy unit 114 transmits a notificationsignal to the mobile device 100 and the notification box 406 andacknowledgment input 408 is displayed on the touchscreen 122. Theintelligent input classifier 502 will filter any detected anomalousinputs detected once the autonomy unit 114 receives confirmation of theacknowledgment input 408.

FIG. 5 is a block diagram of the mobile device 100 and the vehicle 102.As illustrated in FIG. 5, the mobile device 100 includes the touchscreen122, a controller 504, a remote parking application 506 (i.e., app), andthe communication module 120. The controller 504 is communicativelycoupled to the remote parking app 506, the touchscreen 122, and thecommunication module 120 within the mobile device 100. The autonomy unit114 and the communication module 116 are communicatively coupledtogether within the vehicle 102. Further, the communication module 120of the mobile device 100 and the communication module 116 of the vehicle102 are communicatively coupled together (e.g., via wirelesscommunication). Further, as illustrated FIG. 5, the touchscreen 122includes a display 508 and sensors 510. The display 508 presents theinterface(s) to the user 118 of the mobile device 100, and the sensors510 (e.g., capacitive sensors, resistance sensors) detect input(s)provided by the user 118 to the touchscreen 122 of the mobile device100. Furthermore, the autonomy unit 114 of the vehicle 102 includes aninput classifier 502 configured to analyze and/or classify input(s)detected by the touchscreen 122. In some examples, the input classifier502 analyzes the received input(s) to determine whether the input isconsistent with a mode of the remote parking app 506 such as, unlockand/or initiation, continuous input verification, and other such modes.In some examples the input classifier 502 is configured as anintelligent input classifier where the received input(s) is/are fed intoa support vector machine, an artificial neural network, a convolutionalneural network, and other such intelligent classifiers. As such, theintelligent input classifier 502 is trained or otherwise programmed toinclude input data from known nominal inputs and input data from knownunintentional and/or anomalous inputs (e.g., input with wet/dirty hands,input wearing gloves, input from user holding edge of mobile device 100,and other random inputs).

In operation, the controller 504 presents an interface (e.g., theinterface 200 of FIG. 2) of the remote parking app 506 to the user 118via the display 508 of the touchscreen 122. As the interface is beingpresented, the controller 504 receives an input (e.g., a dragging motionalong the touchscreen 122 such as within along the motion track 202 ofFIG. 2) provided by the user 118 for initiating remote parking of thevehicle 102. For example, the sensors 510 of the touchscreen 122 detectthe input provided by the user 118. The controller 504 of the mobiledevice 100 sends a signal (e.g., a first signal) to the autonomy unit114 of the vehicle 102 via the communication module 120 and thecommunication module 116 to initiate remote parking of the vehicle 102.

While the interface is presented on the touchscreen 122, the controller504 monitors whether the remote parking app 506 continues to receive aninput. In some examples, the controller 504 prompts the remote parkingapp 506 to send a signal to the controller 504 upon the presentation ofthe interface and the detection of a nominal input. In other examples,the remote parking app 506 sends the signal to the controller 504 uponpresentation of the interface and the detection of an unintended and/oranomalous input. For example, the remote parking app 506 sends a firstinput signal (e.g., a digital data of ‘0’) to the controller 504 thatindicates the remote parking app 506 has received a nominal input. Theremote parking app 506 sends a second input signal (e.g., a digital dataof ‘1’) to the controller 504 that indicates the remote parking app 506has received an unintended and/or anomalous input. The remote parkingapp 506 continuing to receive the second data input signal (e.g., thedata signal of ‘1’) indicates that the touchscreen 122 is detecting orotherwise receiving unintended and/or anomalous inputs.

To prevent the autonomy unit 114 from continuing to remotely park thevehicle 102 while the remote parking app 504 is detecting anomalousand/or unintended inputs, the controller 504 sends the signal (e.g., thesecond signal) to the vehicle 102 and the autonomy unit 114 pauses orhalts the remote parking of the vehicle 102 in response to detection ofthe unintended and/or anomalous input. In some examples, the controller504 stops sending the signal (e.g., the first signal) to the autonomyunit 114 to stop initiating the remote parking. In other examples, thecontroller 502 sends another signal (e.g., a second signal) to theautonomy unit 114 via the communication module 120 and the communicationmodule 116 to stop initiating the remote parking.

FIG. 6 is a block diagram of electronic components 600 of the mobiledevice 100. As illustrated in FIG. 6, the electronic components 600include the controller 504, memory 602, the communication module 120,and the touchscreen 122 that includes the display 508 and the sensors510.

The controller 504 may be any suitable processing device or set ofprocessing devices such as, but not limited to, a microprocessor, amicrocontroller-based platform, an integrated circuit, one or more fieldprogrammable gate arrays (FPGAs), and/or one or moreapplication-specific integrated circuits (ASICs).

The memory 602 may be volatile memory (e.g., RAM including non-volatileRAM, magnetic RAM, ferroelectric RAM, etc.), non-volatile memory (e.g.,disk memory, FLASH memory, EPROMs, EEPROMs, memristor-based non-volatilesolid-state memory, etc.), unalterable memory (e.g., EPROMs), read-onlymemory, and/or high-capacity storage devices (e.g., hard drives, solidstate drives, etc). In some examples, the memory 602 includes multiplekinds of memory, particularly volatile memory and non-volatile memory.

The memory 602 is computer readable media on which one or more sets ofinstructions, such as the software for operating the methods of thepresent disclosure, can be embedded. The instructions may embody one ormore of the methods or logic as described herein. For example, theinstructions reside completely, or at least partially, within any one ormore of the memory 602, the computer readable medium, and/or within thecontroller 504 during execution of the instructions. For example, theremote parking app 506 of FIG. 5 includes one or more sets ofinstructions that are embedded on the memory 602 and are executed by thecontroller 504.

The terms “non-transitory computer-readable medium” and“computer-readable medium” include a single medium or multiple media,such as a centralized or distributed database, and/or associated cachesand servers that store one or more sets of instructions. Further, theterms “non-transitory computer-readable medium” and “computer-readablemedium” include any tangible medium that is capable of storing, encodingor carrying a set of instructions for execution by a processor or thatcause a system to perform any one or more of the methods or operationsdisclosed herein. As used herein, the term “computer readable medium” isexpressly defined to include any type of computer readable storagedevice and/or storage disk and to exclude propagating signals.

FIG. 7 is a block diagram of electronic components 700 of the vehicle102. As illustrated in FIG. 7, the electronic components 700 include anon-board computing platform 702, the communication module 116, sensors704, electronic control units (ECUs) 706, and a vehicle data bus 708.

The on-board computing platform 702 includes a microcontroller unit,controller or processor 710 and memory 712. The processor 710 may be anysuitable processing device or set of processing devices such as, but notlimited to, a microprocessor, a microcontroller-based platform, anintegrated circuit, one or more field programmable gate arrays (FPGAs),and/or one or more application-specific integrated circuits (ASICs). Thememory 712 may be volatile memory (e.g., RAM including non-volatile RAM,magnetic RAM, ferroelectric RAM, etc.), non-volatile memory (e.g., diskmemory, FLASH memory, EPROMs, EEPROMs, memristor-based non-volatilesolid-state memory, etc.), unalterable memory (e.g., EPROMs), read-onlymemory, and/or high-capacity storage devices (e.g., hard drives, solidstate drives, etc.). In some examples, the memory 712 includes multiplekinds of memory, particularly volatile memory and non-volatile memory.

The memory 712 is computer readable media on which one or more sets ofinstructions, such as the software for operating the methods of thepresent disclosure, can be embedded. The instructions may embody one ormore of the methods or logic as described herein. For example, theinstructions reside completely, or at least partially, within any one ormore of the memory 712, the computer readable medium, and/or within theprocessor 710 during execution of the instructions.

The terms “non-transitory computer-readable medium” and“computer-readable medium” include a single medium or multiple media,such as a centralized or distributed database, and/or associated cachesand servers that store one or more sets of instructions. Further, theterms “non-transitory computer-readable medium” and “computer-readablemedium” include any tangible medium that is capable of storing, encodingor carrying a set of instructions for execution by a processor or thatcause a system to perform any one or more of the methods or operationsdisclosed herein. As used herein, the term “computer readable medium” isexpressly defined to include any type of computer readable storagedevice and/or storage disk and to exclude propagating signals.

The sensors 704 are arranged in and around the vehicle 102 to monitorproperties of the vehicle 102 and/or an environment in which the vehicle102 is located. One or more of the sensors 704 may be mounted to measureproperties around an exterior of the vehicle 102. Additionally oralternatively, one or more of the sensors 704 may be mounted inside acabin of the vehicle 102 or in a body of the vehicle 102 (e.g., anengine compartment, wheel wells, etc.) to measure properties in aninterior of the vehicle 102. For example, the sensors 704 includeaccelerometers, odometers, tachometers, pitch and yaw sensors, wheelspeed sensors, microphones, tire pressure sensors, biometric sensorsand/or sensors of any other suitable type.

In the illustrated example, the sensors 704 include a camera 714, aRADAR sensor 716, a LIDAR sensor 718, and a vehicle speed sensor 720.For example, the camera 714 obtains image(s) and/or video to enabledetection and location of nearby object(s). The RADAR sensor 716 detectsand locates the nearby object(s) via radio waves, and the LIDAR sensor718 detects and locates the nearby object(s) via lasers. The camera 714,the RADAR sensor 716, and/or the LIDAR sensor 718 monitor an areasurrounding the vehicle 102 to facilitate autonomous parking of thevehicle 102 into the available parking spot 104. Further, the vehiclespeed sensor 720 monitors a speed of the vehicle 102 to facilitateautonomous parking of the vehicle 102 into the available parking spot104.

The ECUs 706 monitor and control the subsystems of the vehicle 102. Forexample, the ECUs 706 are discrete sets of electronics that includetheir own circuit(s) (e.g., integrated circuits, microprocessors,memory, storage, etc.) and firmware, sensors, actuators, and/or mountinghardware. The ECUs 706 communicate and exchange information via avehicle data bus (e.g., the vehicle data bus 708). Additionally, theECUs 706 may communicate properties (e.g., status of the ECUs 706,sensor readings, control state, error and diagnostic codes, etc.) toand/or receive requests from each other. For example, the vehicle 102may have seventy or more of the ECUs 706 that are positioned in variouslocations around the vehicle 102 and are communicatively coupled by thevehicle data bus 708.

In the illustrated example, the ECUs 706 include the autonomy unit 114and a body control module 722. The autonomy unit 114 autonomouslycontrols motive functions of the vehicle 102, for example, to remotelypark the vehicle 102 in the available parking spot 104. The body controlmodule 722 controls one or more subsystems throughout the vehicle 102,such as power windows, power locks, an immobilizer system, powermirrors, etc. For example, the body control module 722 includes circuitsthat drive one or more of relays (e.g., to control wiper fluid, etc.),brushed direct current (DC) motors (e.g., to control power seats, powerlocks, power windows, wipers, etc.), stepper motors, LEDs, etc.

The vehicle data bus 708 communicatively couples the communicationmodule 116, the on-board computing platform 702, the sensors 704, andthe ECUs 706. In some examples, the vehicle data bus 708 includes one ormore data buses interconnected by a gateway. The vehicle data bus 708may be implemented in accordance with a controller area network (CAN)bus protocol as defined by International Standards Organization (ISO)11898-1, a Media Oriented Systems Transport (MOST) bus protocol, a CANflexible data (CAN-FD) bus protocol (ISO 11898-7) and/a K-line busprotocol (ISO 9141 and ISO 14230-1), and/or an Ethernet™ bus protocolIEEE 802.3 (2002 onwards), etc.

FIG. 8 is a flowchart of an example method 800 to verify providefeedback to input received on an interface of a mobile device for remoteparking of a vehicle in accordance with the teachings herein. Theflowchart of FIG. 8 is representative of machine readable instructionsthat are stored in memory (such as the memory 602 of FIG. 6) and includeone or more programs that are executed by a processor (such as thecontroller 504 of FIGS. 5 and 6) of the mobile device 100 of FIGS. 1 and5 and 6. Additionally or alternatively, the flowchart of FIG. 8 isrepresentative of machine readable instructions that are stored inmemory (such as the memory 712 of FIG. 7) and include one or moreprograms which, when executed by a processor (such as the processor 710of FIG. 7), cause the autonomy unit 114 to remotely park the vehicle 102of FIGS. 1, 5, and 7. While the example program is described withreference to the flowchart illustrated in FIG. 8, many other methods ofverifying a remote parking interface on a mobile device mayalternatively be used. For example, the order of execution of the blocksmay be rearranged, changed, eliminated, and/or combined to perform themethod 800. Further, because the method 800 is disclosed in connectionwith the components of FIGS. 1-7, some functions of those componentswill not be described in detail below.

Initially, at block 802, the controller 504 of the mobile device 100presents an interface (e.g., the interface 200 of FIG. 2) of the remoteparking app 506 to the user 118 via the display 508 of the touchscreen122. At block 804, the controller 504 determines whether an input hasbeen detected or otherwise received via the sensors 510 of thetouchscreen 122 while the interface is being presented. In response tothe controller 504 determining that an input has not been received fromthe user 118, the method 800 remains at block 804. Otherwise, inresponse to the controller 504 determining that an input (e.g., touchingof initiation input 212, a dragging motion along the touchscreen 122such as within along the motion path 204 of FIG. 2) has been received,the method 800 proceeds to block 806.

At block 806, the controller 504 of the mobile device 100 sends aninstruction (e.g., a first signal) to the autonomy unit 114 of thevehicle 102 via the communication module 120 and the communicationmodule 116 to initiate remote parking of the vehicle 102. The autonomyunit 114 includes the input classifier 502 that determines whether theinput is detected within a certain range or area of the display 508(e.g., within the motion track 202 and confidence band 216) or the inputis detected outside the certain range. At block 808, the autonomy unit114 and the input classifier 502 classify the input as being a nominalinput or an anomalous input.

At block 810, the autonomy unit 114 determines whether the sensors 508of the touchscreen 122 have continuously received a nominal input fromthe user 118 consistent with performing remote parking of the vehicle.In response to determining the autonomy unit 114 classified the input asa nominal input, the method 800 proceeds to block 812. At block 812 theautonomy unit 114 sends a signal to the mobile device 100 to initiateand/or continue the remote parking of the vehicle 102.

Referring back to block 810, in response to determining the autonomyunit 114 classified the input as an anomalous and/or unintended input,the method 800 proceeds to block 814. At block 814, the autonomy unit114 sends a notification (e.g., notification box 406 of FIG. 4B) to themobile device 100 indicating to the user that an anomalous input wasdetected. The notification box 406 includes an acknowledgment input(e.g., acknowledgement input 408 of FIG. 4B) that requires the user 118of the mobile device 100 to provide an input to the touchscreen 122 toconfirm the notification box 406 was received.

At block 816, the controller 504 determines whether the notification wasreceived and/or acknowledged by the user. In response to the controller504 determining the notification acknowledgment was received from theuser 118, the remote parking app 506 returns to block 802 and continuesto present the interface to the user 118 such that the user is able toproceed with remote parking the vehicle 102.

In response to the controller 504 determining the notificationacknowledgment was not received from the user, the method 800 proceedsto block 818 at which the controller 504 continues to send theinstruction (e.g., a second signal) to the vehicle 102 to stop or pauseremote parking of the vehicle 102. At block 820, the autonomy unit 114terminates or aborts the remote parking of the vehicle 102.

In this application, the use of the disjunctive is intended to includethe conjunctive. The use of definite or indefinite articles is notintended to indicate cardinality. In particular, a reference to “the”object or “a” and “an” object is intended to denote also one of apossible plurality of such objects. Further, the conjunction “or” may beused to convey features that are simultaneously present instead ofmutually exclusive alternatives. In other words, the conjunction “or”should be understood to include “and/or”. The terms “includes,”“including,” and “include” are inclusive and have the same scope as“comprises,” “comprising,” and “comprise” respectively.

The above-described embodiments, and particularly any “preferred”embodiments, are possible examples of implementations and merely setforth for a clear understanding of the principles of the invention. Manyvariations and modifications may be made to the above-describedembodiment(s) without substantially departing from the spirit andprinciples of the techniques described herein. All modifications areintended to be included herein within the scope of this disclosure andprotected by the following claims.

What is claimed is:
 1. A vehicle system comprising: a mobile deviceincluding a controller and a touchscreen configured to present aninterface of a remote parking app, wherein the controller receives aninput responsive to the remote parking app; a vehicle autonomy unitcommunicably coupled to the mobile device to receive an input signalwhich corresponds with the received input; and an input classifiercoupled to the vehicle autonomy unit, wherein the input classifierverifies the received input signal complies with an inputclassification, and wherein the vehicle autonomy unit sends anotification to the mobile device if the received input signal isnon-compliant with the input classification.
 2. The vehicle system ofclaim 1, wherein a compliant input is defined as a nominal input by theinput classification, and wherein a non-compliant input is defined as ananomalous input by the input classification.
 3. The vehicle system ofclaim 2, wherein the input classification includes a timer that startsafter presentation of the interface, and wherein the notification ispresented when a predefined number of anomalous inputs are detectedwithin a predetermined length of time, as measured by the timer.
 4. Thevehicle system of claim 2, wherein the interface includes a motion trackand the mobile device receives the input when the touchscreen detects adragging motion within the motion track, and wherein the nominal inputis detected within the motion track and the anomalous input is detectedoutside of the motion track.
 5. The vehicle system of claim 4, whereinthe nominal input is a continuous input detected within a definedconfidence band surrounding the motion track, and wherein the anomalousinput is an arbitrary and non-continuous input detected inside oroutside the defined confidence band surrounding the motion track.
 6. Thevehicle system of claim 1, wherein the notification includes anacknowledgement input and the acknowledgement input is detected, by themobile device, to verify the interface is capable of producing anintended input.
 7. The vehicle system of claim 1, wherein the inputclassification includes an intelligent input classification programmedwith a known set of input data that defines the received input as one ofa nominal input and an anomalous input.
 8. The vehicle system of claim7, wherein the intelligent input classification identifies a source ofthe anomalous input, based on analysis between the anomalous input andthe known set of input data, and wherein the notification includes anidentification of the source of the anomalous input.
 9. A method forverifying inputs for remote parking of vehicles comprising: presenting,via a touchscreen of a mobile device, an interface of a remote parkingapp; receiving an input at a controller of the mobile device via thetouchscreen responsive to presenting the interface; receiving, by avehicle autonomy unit, an input signal sent by the mobile device;verifying, by an input classifier, the received input signal complieswith an input classification; and sending, via the vehicle autonomyunit, a notification to the mobile device if the received input signalis non-compliant with the input classification.
 10. The method of claim9, wherein verifying the received input by the input classifier includesdefining a compliant input as a nominal input and defining anon-compliant input as an anomalous input.
 11. The method of claim 10,further including starting a timer after presenting the interface,wherein presenting the notification occurs when a predefined number ofanomalous inputs are detected within a predetermined length of time, asmeasured by the timer.
 12. The method of claim 10, wherein presentingthe interface includes presenting a motion track and receiving the inputvia the touchscreen includes detecting a dragging motion within themotion track, and wherein the nominal input is classified by detectingthe dragging motion within the motion track and the anomalous input isclassified by detecting the dragging motion outside of the motion track.13. The method of claim 12, wherein the nominal input is a continuousinput detected within a defined confidence band surrounding the motiontrack, and wherein the anomalous input is an arbitrary andnon-continuous input detected inside and outside the defined confidenceband surrounding the motion track.
 14. The method of claim 9, whereinpresenting the notification includes presenting an acknowledgementinput, and wherein the acknowledgement input is detected, by thecontroller, to verify the interface is capable of producing an intendedinput.
 15. The method of claim 9, wherein the input classificationincludes an intelligent input classification programmed with a known setof input data defining the received input as one of a nominal input andan anomalous input.
 16. The method of claim 15, further includingidentifying a source of the anomalous input, based on an analysisbetween the anomalous input and the known set of input data, whereinpresenting the notification includes presenting an identification of thesource of the anomalous input.
 17. A tangible computer readable mediumincluding instructions which, when executed, cause a machine to:present, via a touchscreen of a mobile device, an interface of a remoteparking app; receive an input at a controller of the mobile device viathe touchscreen responsive to presenting the interface; receive, by avehicle autonomy unit, an input signal sent by the mobile device verify,by an input classifier, the received input signal complies with an inputclassification; and send, via the vehicle autonomy unit, a notificationto the mobile device if the received input signal is non-compliant withthe input classification.
 18. The tangible computer readable medium ofclaim 17, wherein a compliant input is defined as a nominal input by theinput classification, and wherein a non-compliant input is defined as ananomalous input by the input classification.
 19. The tangible computerreadable medium of claim 18, wherein the interface includes a motiontrack and the controller receives the input when the touchscreen detectsa dragging motion within the motion track, and wherein the nominal inputis detected within the motion track and the anomalous input is detectedoutside of the motion track.
 20. The tangible computer readable mediumof claim 17, wherein the notification includes an acknowledgement inputand an activation of the acknowledgement input is received, by thecontroller, to verify the interface is capable of producing an intendedinput.